Skip to content

Update korthout/backport-action action to v4.7.2 - #248

Closed
renovate[bot] wants to merge 1 commit into
developfrom
renovate/korthout-backport-action-4.x
Closed

renovate[bot] wants to merge 1 commit into
developfrom
renovate/korthout-backport-action-4.x

Conversation

@renovate

@renovate renovate Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
korthout/backport-action action patch v4.7.1 → v4.7.2

Release Notes

korthout/backport-action

v4.7.2: Backport-action v4.7.2

Compare Source

What's Changed

Thanks to two contributions by @​bahimehdi, this release fixes two bugs. Neither needs any configuration.

With comment_style: legacy, the action posts an explanatory comment when the original pull request isn't merged, or when it contains merge commits with merge_commits: fail. Previously, if GitHub rejected that comment, the job could crash. Now the action logs the failure and doesn't fail the job, as it already did for the summary comment.

With merge_commits: skip, a pull request that contains only merge commits was reported as a failed backport for every target branch, with instructions to cherry-pick no commits. With experimental.conflict_resolution: draft_commit_conflicts, the action instead pushed an unchanged backport branch for each target branch. Now the action explains once, on the original pull request, that there is nothing to backport and why, and doesn't touch any target branch. It sets was_successful to true, as it does when every target branch already contains the changes. With comment_style: summary, that looks like this:

Backport-action found nothing left to backport from this pull request in workflow run 123.

This pull request contains only merge commits, and merge_commits: skip excludes them.

The summary comment also no longer says "backported this pull request" when every target branch was skipped, for example because its backport pull request already exists. It now says "found nothing left to backport from this pull request".

The README now explains how to run CI on your backport pull requests right away. With the default GITHUB_TOKEN, CI doesn't run on backport pull requests, or its runs wait for approval. The new Run CI on backport pull requests section shows how to give the action a GitHub App token instead, and pass it to both actions/checkout and the action. The README also explains what public repositories need to do before GitHub blocks pull_request_target on December 2, 2026: allow the event for the backport workflow in an Actions policy (and issue_comment too, if you trigger backports with a comment).

New Contributors

Maintenance changes

Full Changelog: korthout/backport-action@v4.7.1...v4.7.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from YongDo-Hyun as a code owner November 11, 2026 09:48
@renovate
renovate Bot deleted the renovate/korthout-backport-action-4.x branch November 17, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant